chore: update CODEOWNERS comments to match org standard format - #259

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

@petry-projects/org-leads — this PR is ready for review and merge.

Summary: The CODEOWNERS file was already compliant (owner line * @petry-projects/org-leads was in place since #252). This PR updates the inline comments to directly reference the standard URL and state the org-leads-first rule, formally closing the false-positive compliance audit finding in #254.

The diff is comments-only — no functional changes.

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@dev-lead - please fix this PR

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved manually.

Please resolve the conflicts and push:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

Review — fix requested (cycle 1/3)

The automated review identified the following issues. Please address each one:

Findings to fix

Automated review — NEEDS HUMAN REVIEW

Risk: LOW
Reviewed commit: a865057438833880482ce6bf0ac2474ac0d958ed
Review mode: triage-approved (single reviewer)

Summary

This PR makes a comments-only change to .github/CODEOWNERS (3 additions, 2 deletions, 1 file). The functional owner line * @petry-projects/org-leads is unchanged; the diff replaces the existing standard-reference comment with a direct URL to petry-projects/.github/standards/codeowners-standard.md, adds an explicit rule line stating @petry-projects/org-leads must be first on every owner line, and inserts a # Default — all paths section header. The triage tier's LOW-risk classification is confirmed: no ownership behavior changes, comments only.

Approval is held back solely because the PR cannot merge in its current state — it has unresolved conflicts with main.

Linked issue analysis

Closes #254 — a CODEOWNERS compliance audit finding that the PR description identifies as a false-positive (audit script misread gh_api retry stdout as file content). The owner line was already compliant after #252. This PR resolves the audit by making the standard reference and org-leads-first rule self-evident inline, which is a reasonable way to formally close a recurring false-positive finding. The linked issue is substantively addressed.

Findings

Blocker — merge conflict (must be resolved by a human):

• mergeable: CONFLICTING, mergeStateStatus: DIRTY.
• The auto-rebase bot posted a conflict notice on 2026-05-21 (<!-- auto-rebase-conflict -->) instructing manual git merge origin/main + conflict resolution.
• The PR author already asked for help on 2026-05-20: "@dev-lead - please fix this PR". This is an unanswered human request directed at a reviewer.
• 15 of the 16 commits on this branch are bot-generated Merge branch 'main' merges, suggesting repeated unsuccessful auto-rebase attempts. A human should resolve the conflict and consider squashing the merge noise before re-review.

Non-blocking observations:

• Change is content-LOW-risk: comments only, owner assignment unchanged, strengthens (does not relax) the org-leads-first rule.
• The existing Copilot reviewer comment (2026-05-08) accurately summarizes the change and raised no concerns.
• The earlier db4af21 head (per CodeRabbit's snapshot) is not the current head; CodeRabbit hit a rate limit and did not re-review at a865057. Not a blocker but worth noting.

CI status

All checks green at a865057438833880482ce6bf0ac2474ac0d958ed:

• CodeQL — Analyze (actions) ✓
• CodeQL — Analyze (javascript-typescript) ✓
• CodeQL — Analyze (python) ✓
• CodeQL ✓
• CodeRabbit ✓
• SonarQube Cloud — Quality Gate Passed (0 new issues, 0 security hotspots) ✓

Reviewed automatically by the PR-review agent (single-reviewer mode: opus 4.7). Reply if you need a human review.

Additional tasks

1. Resolve all unresolved review thread comments from other reviewers
2. Ensure all CI checks pass after your changes
3. Rebase on the target branch if behind
4. Do NOT modify files unrelated to the findings above

The review cascade will automatically re-review after new commits are pushed.

Closing due to merge conflict that cannot be auto-rebased. Re-implementing from fresh main via dev-lead.